Skip to content

Conversation

@rvedotrc
Copy link
Contributor

@rvedotrc rvedotrc commented Apr 21, 2025

No description provided.

@adamblanchard
Copy link
Contributor

Can you link this on the issue for transparency #4

@rvedotrc rvedotrc moved this to In review in Curriculum Crew Apr 21, 2025
@rvedotrc rvedotrc moved this from In review to In progress in Curriculum Crew Apr 21, 2025
@adamblanchard
Copy link
Contributor

If it's not trivial to fix, then it is not a priority right now.

The first milestone that we have to hit in this project is to reuse existing content in it's current form. Linting is therefore an optional requirement in this initial scope.

If it's relatively reasonable to fix now, then I'm all for it. However, until we have a plan for the js content it might be best to hold off any changes to legacy content in case we modify it a lot.

@rvedotrc
Copy link
Contributor Author

I don't suppose it'll take more than a couple of hours to fix up. It's just, significantly messier (lint-wise) than the other modules.

@rvedotrc rvedotrc changed the base branch from legacy to main April 21, 2025 10:14
needs a lot of fixing
Not ready yet: any links starting `/` need to be rewritten
@rvedotrc rvedotrc marked this pull request as ready for review April 21, 2025 11:22
@rvedotrc rvedotrc moved this from In progress to In review in Curriculum Crew Apr 22, 2025
@adamblanchard adamblanchard merged commit d792316 into main Apr 25, 2025
1 check passed
@rvedotrc rvedotrc deleted the js-legacy branch April 26, 2025 16:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In review

Development

Successfully merging this pull request may close these issues.

4 participants